NAME¶

git-fetch - Download objects and refs from another repository

SYNOPSIS¶

git fetch [<options>] [<repository> [<refspec>...]]

git fetch [<options>] <group>

git fetch --multiple [<options>] [<repository> | <group>]...

git fetch --all [<options>]

DESCRIPTION¶

Fetches named heads or tags from one or more other repositories, along with the objects necessary to complete them.

The ref names and their object names of fetched refs are stored in .git/FETCH_HEAD. This information is left for a later merge operation done by git merge.

When <refspec> stores the fetched result in tracking branches, the tags that point at these branches are automatically followed. This is done by first fetching from the remote using the given <refspec>s, and if the repository has objects that are pointed by remote tags that it does not yet have, then fetch those missing tags. If the other end has tags that point at branches you are not interested in, you will not get them.

git fetch can fetch from either a single named repository, or or from several repositories at once if <group> is given and there is a remotes.<group> entry in the configuration file. (See git-config(1)).

OPTIONS¶

--all

-a, --append

--depth=<depth>

--dry-run

-f, --force

-k, --keep

--multiple

--prune

-n, --no-tags

-t, --tags

-u, --update-head-ok

--upload-pack <upload-pack>

-q, --quiet

-v, --verbose

--progress

<repository>

<group>

<refspec>

GIT URLS¶

In general, URLs contain information about the transport protocol, the address of the remote server, and the path to the repository. Depending on the transport protocol, some of this information may be absent.

Git natively supports ssh, git, http, https, ftp, ftps, and rsync protocols. The following syntaxes may be used with them:

An alternative scp-like syntax may also be used with the ssh protocol:

The ssh and git protocols additionally support ~username expansion:

For local respositories, also supported by git natively, the following syntaxes may be used:

These two syntaxes are mostly equivalent, except when cloning, when the former implies --local option. See git-clone(1) for details.

When git doesn’t know how to handle a certain transport protocol, it attempts to use the remote-<transport> remote helper, if one exists. To explicitly request a remote helper, the following syntax may be used:

where <address> may be a path, a server and path, or an arbitrary URL-like string recognized by the specific remote helper being invoked. See git-remote-helpers(1) for details.

If there are a large number of similarly-named remote repositories and you want to use a different format for them (such that the URLs you use will be rewritten into URLs that work), you can create a configuration section of the form:

        [url "<actual url base>"]


                insteadOf = <other url base>

For example, with this:

        [url "git://git.host.xz/"]


                insteadOf = host.xz:/path/to/


                insteadOf = work:

a URL like "work:repo.git" or like "host.xz:/path/to/repo.git" will be rewritten in any context that takes a URL to be "git://git.host.xz/repo.git".

If you want to rewrite URLs for push only, you can create a configuration section of the form:

        [url "<actual url base>"]


                pushInsteadOf = <other url base>

For example, with this:

        [url "ssh://example.org/"]


                pushInsteadOf = git://example.org/

a URL like "git://example.org/path/to/repo.git" will be rewritten to "ssh://example.org/path/to/repo.git" for pushes, but pulls will still use the original URL.

REMOTES¶

The name of one of the following can be used instead of a URL as <repository> argument:

All of these also allow you to omit the refspec from the command line because they each contain a refspec which git will use by default.

        [remote "<name>"]


                url = <url>


                pushurl = <pushurl>


                push = <refspec>


                fetch = <refspec>

        URL: one of the above URL format


        Push: <refspec>


        Pull: <refspec>

        <url>#<head>

        refs/heads/<head>:refs/heads/<branch>

        HEAD:refs/heads/<head>

EXAMPLES¶

$ git fetch origin

$ git fetch origin +pu:pu maint:tmp

SEE ALSO¶

git-pull(1)

AUTHOR¶

Written by Linus Torvalds <torvalds@osdl.org[1]> and Junio C Hamano <gitster@pobox.com[2]>

DOCUMENTATION¶

Documentation by David Greaves, Junio C Hamano and the git-list <git@vger.kernel.org[3]>.

GIT¶

Part of the git(1) suite

NOTES¶

1.

torvalds@osdl.org

2.

gitster@pobox.com

3.

git@vger.kernel.org